Event ticket hub

ABSTRACT

There are provided methods and systems to retrieve search result information and digital content. The system receives input information identifying a plurality of data sources from which to retrieve digital content. Next the system retrieves search result information, over the network, from the plurality of data sources based on the input information. Next the system retrieves the digital content, over the network, from at least one of the data sources based on the search result information. Finally, the system communicates digital content to a client machine.

PRIORITY

This application is a Continuation of and claims the benefit of priorityto U.S. patent application Ser. No. 13/552,935, filed Jul. 19, 2012,which is a continuation of application Ser. No. 11/779,022, filed Jul.17, 2007, both of which are hereby incorporated by reference in theirentirety.

FIELD

Embodiments relate generally to the technical field of datacommunications and, in one example embodiment, to methods and systems toretrieve search result information and digital content.

BACKGROUND

Searching for information and digital content on a network presents manychallenges. One challenge is the time required to find and retrieve thedesired information and digital content. For example, a user may consumeconsiderable time operating a personal computer to visit web sites andmedia stores to locate specific types of digital content. Further,requesting delivery of digital content that is published to a feed mayalso require time to locate the feed and time to filter undesirableinformation and digital content that is published to the feed. Otherchallenges include organizing, storing, and budgeting payments fordigital content.

BRIEF DESCRIPTION OF DRAWINGS

The present invention is illustrated by way of example and notlimitation in the figures of the accompanying drawings, in which likereferences indicate similar elements and in which:

FIG. 1 is a network diagram depicting a system, according to one exampleembodiment, having a client-server architecture;

FIG. 2 is a block diagram illustrating modules and an engine, accordingto an embodiment, at a digital content hub;

FIG. 3 is a block diagram illustrating modules, according to anembodiment, at a control node;

FIG. 4 is a block diagram illustrating modules, according to anembodiment, at a portable control node;

FIG. 5 is a block diagram illustrating a data flow, according to anembodiment;

FIG. 6 is a block diagram illustrating a database, according to anembodiment, coupled to the digital content hub;

FIG. 7 is a block diagram illustrating input information, according toan embodiment;

FIG. 8 is a block diagram illustrating search information, according toan embodiment;

FIG. 9 is a block diagram illustrating filter information, according toan embodiment;

FIG. 10 is a block diagram illustrating output information, according toan embodiment;

FIG. 11 is a block diagram illustrating target information, according toan embodiment;

FIG. 12 is a block diagram illustrating a database, according to anembodiment, coupled to the control node;

FIG. 13 is a block diagram illustrating a database, according to anembodiment, coupled to the portable control node;

FIG. 14 is a flow chart illustrating a method, according to anembodiment, to retrieve search result information and digital content;

FIG. 15 is a flow chart illustrating a method, according to anembodiment, to retrieve search result information;

FIG. 16 is a flow chart illustrating a method, according to anembodiment, to retrieve digital content;

FIG. 17 is a flow chart illustrating a method, according to anembodiment, to identify digital content to retrieve;

FIG. 18 is a flow chart illustrating a method, according to anembodiment, to communicate digital content to the portable control node;

FIG. 19 is a flow chart illustrating a method, according to anembodiment, to receive input information from the portable control nodeand communicate the input information to the control node;

FIGS. 20-28 are diagrams illustrating user interfaces, according to anembodiment;

FIG. 29 is a block diagram of a machine, according to an exampleembodiment, including instructions to perform any one or more of themethodologies described herein.

DETAILED DESCRIPTION

In the following description, for purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of an embodiment of the present invention. It will beevident, however, to one skilled in the art that the present inventionmay be practiced without these specific details.

FIG. 1 is a network diagram depicting a system 10, according to oneexample embodiment to retrieve and communicate output informationincluding digital content. The system 10 is shown to include a servermachine 12 (e.g., digital content hub), data sinks 14, and data sources18. Broadly, the server machine 12 (e.g., digital content hub) receivesinput information over a network 16 (e.g., Internet) from the data sinks14 and periodically retrieves output information including digitalcontent, over the network 16, from multiple data sources 18 based on theinput information before communicating the retrieved output information,over the network 16, to the data sinks 14. The server machine 12 mayreceive the input information from a user that operates the data sinks14 and may store the input information on a database 23 for continualand periodic retrieval of the digital content and other outputinformation. In addition, the server machine 12 may also be authorizedby the data sinks 14 to make a payment, over the network 16, to apayment system 20 as required for the retrieval of the outputinformation including the digital content. Accordingly, the retrievedoutput information is targeted to the tastes and preferences of theuser. This may serve to automate and streamline the tasks required tocontinually identify, filter, and retrieve digital content and otheroutput information, that are of interest to the user.

The data sinks 14 may include a client machine 22 (e.g., control node)and portable data sinks 24. The data sinks 14 may be used to request,store, manage, and play digital content. The portable data sinks 24include portable client machines 32 (e.g., IPOD or other content storageand reproduction devices). The client machine 22 may operate as acontrol node that may receive input information from a user andcommunicate the input information to the digital content hub that, inturn, uses the input information to retrieve the digital content andother output information. The client machine 22 is shown to be coupledto a database 26 for storing the input and output information and amonitor 28 and speaker 30. The portable data sinks 24 are shown toinclude two portable client machines 32. The portable client machines 32are respectively coupled to a monitor 28, speakers 30 and a database 34.The portable client machines 32 may be embodied as an IPOD made by APPLEINC. (Apple Computers) of Cupertino Calif., the BLACKBERRY™ wirelessplatform made by RESEARCH IN MOTION LIMITED (RIM) of Waterloo, Ontarioor any other portable media playing device for playing, managing, andretrieving digital content.

The data sources 18 include server machines 36 respectively coupled todatabases 38. In various embodiments the server machines 36 may hostsearch engines such as the GOOGLE™ search engine by GOOGLE, INC. ofMountain View, Calif., media stores such as the ITUNES media store byAPPLE INC. previously mentioned, network based marketplaces such as thatoperated by EBAY, INC. of San Jose, Calif., multimedia distributionplatforms such as YOUTUBE also by GOOGLE, INC. of or any other networkaccessible platforms for retrieving output information.

Further, while the system 10 shown in FIG. 1 employs a client-serverarchitecture, embodiments are of course not limited to such anarchitecture, and could equally well find application in a distributed,or peer-to-peer, architecture system. The server machine 12 and theclient machine 22 may also host software modules and engines, as laterdescribed, that could also be implemented as standalone softwareprograms, which do not necessarily have networking capabilities.

FIG. 2 is a block diagram illustrating modules at server machine 12(e.g., digital content hub), according to an embodiment. The digitalcontent hub includes a configuration module 50, a processing module 52,a recommendation engine 54 and media modules 56. The configurationmodule 50 receives input information from the user (e.g., control node)or from the portable client machine 32 (e.g., portable control node) viathe client machine 22 and utilizes the input information to generatemetadata information. Further, the configuration module 50 uses themetadata information to retrieve search result information, includingsearch result information entries, from the data sources 18. Theprocessing module 52 may utilize the identified search resultinformation entries (e.g., links to retrieve digital content) toretrieve digital content from the data sources 18. The media modules 56may be used by the configuration module 50 to access the data sources 18to retrieve the search result information. The media modules 56 may alsobe accessed by the processing module 52 to access the data sources 18 toretrieve the digital content. The media modules 56 may be embodied as adigital media player such as the ITUNES digital media player, a browsersuch as the INTERNET EXPLORER offered by MICROSOFT CORPORATION ofRedmond, Wash., an RSS reader such as the GOOGLE RSS READER or any othermodule used to access output information over the network 16.

FIG. 3 is a block diagram illustrating modules at a client machine 22(e.g., control node), according to an embodiment. The client machine 22may include a communication module 58, a distribution module 60, andmedia modules 56. The communication module 58 may be used to receiveinput information from the user and communicate the input information tothe server machine 12 (e.g., digital content hub). In addition, thecommunication module 58 may be used to receive input information fromthe portable client machine 32 (e.g., iPod) and communicate the inputinformation to the server machine 12 (e.g., digital content hub). Thecommunication module 58 may further receive digital content and otheroutput information from the server machine 12 and store such informationto memory or to the database 26.

The distribution module 60 communicates digital content to the portableclient machine 32. In one embodiment the distribution module 60 maycommunicate the digital content to the portable client machine 32 via amedia module 56. In another embodiment the distribution module 60 maycommunicate the digital content to the portable client machine 32 via anApplication Processing Interface (API). The distribution module 60 maycommunicate the digital content responsive to determining a portableclient machine 32 is connected to the client machine 22. In anotherembodiment, the distribution module 60 may communicate the digitalcontent responsive to a user requesting communication of the digitalcontent.

FIG. 4 is a block diagram illustrating modules at a portable clientmachine 32 (e.g., IPOD). The portable client machine 32 includes aportable media module 66. The portable media module 66 may receive inputinformation from a user and communicate the input information to theclient machine 22 (e.g., control node) that, in turn, communicates theinput information to the server machine 12 (e.g., digital content hub).In addition, the portable media module 66 may generate recommendationsfor the acquisition of digital content that are communicated, as inputinformation, to the client machine 22. Further, the portable mediamodule 66 may receive digital content from the client machine 22 (e.g.,control node) and be controlled by the user to manage and play thedigital content.

FIG. 5 is a block diagram illustrating a dataflow 100 for the system 10,according to an embodiment. Illustrated on the left panel are dataprocessing operations performed by a server machine 12 (e.g., digitalcontent hub). Illustrated in the middle panel are data processingoperations performed by a server machine 36 (e.g., data sources 18).Illustrated in the right panel are data processing operations performedby a client machine 22 (e.g., data sink 14). The dataflow 100 moves fromleft to right and starts at the server machine 12 (e.g., digital contenthub).

Broadly, the server machine 12 (e.g., digital content hub) uses inputinformation 102, that has been received from the client machine 22(e.g., control node) or the portable client machine 24 (e.g., iPod) viathe client machine 22, to generate metadata information 104 that, inturn, is used to retrieve output information (e.g., digital content)that is communicated to the client machine 22.

The input information 102 may be contained in an input informationfolder 108 and includes global filter information 110. The inputinformation may describe artists that author the digital content,creations of digital content or categories describing digital content.The global filter information 112 may be used to filter retrieval of thedigital content from the data sources. For example, the global filterinformation may be used to identify digital content that requires apurchase for an amount that exceeds a predetermined purchasinglimitation before retrieving the digital content from the data source18. Further, the global filter information may be used to filterretrieval of digital content that requires storage that exceeds apredetermined storage limitation before retrieving the digital contentfrom the data source 18.

The metadata information 104 includes search result retrieval metadata118, target metadata 120, and digital content retrieval metadata 124.The search result retrieval metadata 118 is used to retrieve searchresults information 145 from the data sources 18. The search resultretrieval metadata 118 includes local command metadata 126 that may beused to generate commands. Examples of such commands include queries toretrieve the search result information 145 that includes search resultinformation entries 121. The commands may be communicated directlythrough an Application Processing Interface to one of the servermachines 36 (e.g., search engine). In another embodiment, the commandsmay be communicated via a media module 56 (e.g., ITUNES) that executeson the server machine 12. For example, the commands may be communicatedto an ITUNES media player to advance the ITUNES media player through aseries of user interfaces and request search result information (e.g.,links to digital content). The ITUNES media player may, in turn,communicate the request for digital content to an ITUNES media store.

The target metadata 120 includes parse metadata 128 and profileinformation 130. The parse metadata 128 may be used by the servermachine 12 (e.g., digital content hub) to parse the search resultinformation 145 to identify target information entries 123 (e.g., linksto digital content, subscriptions to digital content, requestedinformation, links to streaming digital content). The profileinformation 130 may include a history of input information and may beused by the server machine 12 (e.g., digital content hub) to furtheridentify target information entries 123 from the search resultinformation 145. For example, the profile information 130 may be basedon input information 102 that is collected from the user over apredetermined and extended period of time. The profile information 130may be used to generate a recommendation for each of the search resultinformation entries 121.

The digital content retrieval metadata 124 includes remote commandmetadata 132, purchase metadata 134, and storage metadata 136. Theremote command metadata 132 may be used to generate remote commands thatare communicated in association with digital content to the clientmachine 22. The commands may be used at the client machine 22 tocommunicate the digital content to a portable client machine 32 (e.g.,portable music player). For example, the remote command metadata 132 mayinclude commands and/or other information that may be used at the clientmachine 22 to communicate digital content to the portable music player.The purchase metadata 134 may be used by the server machine 12 (e.g.,digital content hub) to determine whether selecting a link to purchasedigital content exceeds a purchase limitation such as a predeterminedprice. The storage metadata 136 may be used by the server machine 12 todetermine whether retrieval of digital content exceeds a storagelimitation such as a predetermined storage limitation.

The output information folder 106 includes target information 147, aspreviously described and digital content 140. The digital content 140may include digital information in the form of movies, albums, songs,digital samples, multimedia presentations, videos, images, etc.

The dataflow is now described. At operation 142, the input information102 that has been previously received from the client machine 22, or theportable client machine 32 via the client machine 22, may be used by theserver machine 12 (e.g., digital content hub) to generate the metadatainformation 104. At operation 144, the metadata information 104 is usedby the server machine 12 (e.g., digital content hub) to retrieve thesearch result information 145. For example, queries may be communicatedto the data sources 18 that, in turn, respond by communicating thesearch result information 145. At operation 146, the target metadata 120is used by the server machine 12 (e.g., digital content hub) to identifysearch result information entries 121 as target information entries 123.In addition, the profile information 130 may be used to generate arecommendation for each of the search result information entries 121.Finally, the search result information entries 121 associated withrecommendations that exceed a predetermined limit may be identified astarget information entries 123, as explained further below.

At operation 148, the digital content retrieval metadata 124 and thetarget information 147 may be used to retrieve digital content from theserver machine(s) 36 (e.g., data sources 18). In some instances, thepurchase metadata 134 and the storage metadata 136 may prohibitretrieval of digital content, as previously described. At operation 149the target information 147 and the digital content 140, with associatedremote commands, may be communicated to the client machine 22.

FIG. 6 is the block diagram illustrating a database 23 according to anembodiment, coupled to the server machine 12 (e.g., digital contenthub). The database 23 may be used to store the input information 102,the metadata information 104, and the output information 106.

FIG. 7 is a block diagram illustrating input information 102, accordingto an embodiment. The input information 102 includes input informationfolders 108 and global filter information 110. The server machine 12(e.g., digital content hub) schedules the retrieval of search resultinformation 145 and associated digital content 140 based on an inputinformation folder 108 granularity. The input information folders 108may be used to store the input information 102 for an artist, acreation, or a category. For example, the input information folder 108may contain artist information 152, creation information 154, orcategory information 156. The artist information 152 may be used toidentify output information 106 (e.g., digital content) associated(e.g., authored, produced, directed, edited, etc.) with an artist (e.g.,Shawn Mullins, Frank Sinatra, Bob Dylan). The creation information 154may be used to retrieve output information 106 associated with acreation (e.g., “Frozen Man,” “Pirates of the Caribbean,” “I Did It MyWay,” etc.). The category information 156 may be used to retrieve outputinformation 106 associated with a category (e.g., Jazz, Jazz Artists,Best Movies of the Year, etc.) of digital content. The artistinformation 152, creation information 154, and category information 156respectively include search information 158 and filter information 160.The search information 158 may be used to retrieve the search resultinformation 145 and identify the target information 147 includingdigital content 140 from the search result information 145. The filterinformation 160 (e.g., predetermined criteria) may be used to determinewhether the identified digital content 140 is prohibited from retrievalfrom the data sources 18.

The global filter information 110 (e.g., predetermined criteria) may beused to apply global filters across the input information folders 108.The global filter information 110 includes recommendation information162, global purchase information 164, and global storage information214. The recommendation information 162 may be used to generaterecommendations from search result information 145, as previouslydescribed. The global purchase information 164 may be used to determinewhether the digital content should be purchased based on a globalfilter. For example, the global filter may include a purchase limitationthat prevents a one time purchase exceeding $50 notwithstanding theartist, creation or category. Another example of a global filter mayinclude a storage rule that applies to multiple artists or a combinationof artists and categories. The global storage information may be used todetermine whether the digital content is retrieved based on a globalfilter that operates as described, but in a context of storagelimitations.

FIG. 8 is a block diagram illustrating search information 158, accordingto an embodiment. The search information 158 includes a folder title200, target identification information 202, search frequency information204, data source information 206, release information 208, and alertinformation 210. The folder title 200 may be input by the user to name acorresponding input and output information folder 108, 106. The targetidentification information 202 may be used to identify different typesof the digital content 140 or other information (e.g., targets) that areof interest to the user. The search frequency information 204 may beused to identify the frequency of initiating retrieval of search resultinformation 145 and associated digital content 140. The data sourceinformation 206 may be used to identify the data sources 18 from whichto retrieve the search result information 145 and the digital content140. The release information 208 may be used to identify whether allreleases of a type of digital content 140 are retrieved or a new release(e.g., not previously released) of digital content is retrieved. Forexample, the input checkbox 624 may receive a request to receive allreleases of a type of digital content 140 and the input checkbox 626 mayreceive a request to receive a new release of digital content 140. Thealert information 210 may be used to communicate an alert to a deviceover the network 16 responsive to predetermined criteria, such asretrieval of digital content.

FIG. 9 is a block diagram illustrating filter information 160, accordingto an embodiment. The filter information 160 includes purchaseinformation 212 and storage information 214 and is used as previouslydescribed but for a single input information folder 108 (e.g., a singleartist, creation, or category).

FIG. 10 is a block diagram illustrating output information 106,according to an embodiment. The output information 106 may includemultiple output information folders 250. The output information folder250 includes a title 252, target information 147 and one or more digitalcontent information 254 entries. The title 252 may be provided by theuser and appears on user interfaces that display the output informationfolder 250. The target information 147 may include search resultinformation 145 and digital content information 245. The digital contentinformation 254 may include digital content 140, as previouslydescribed, and remote command information 258. The remote commandinformation 258 may be communicated with the digital content 140 to theclient machine 22 that, in turn, uses the remote command information 258to communicate the digital content 140 to a portable client machine 32(e.g., iPod).

FIG. 11 is a block diagram illustrating target information 147,according to embodiment. The target information 147 includes digitalcontent link information 268, digital content subscribe information 270,requested information 272 and digital content streaming link information274. The digital content link information 268 may include user interfaceelements (e.g., link) that may be selected to retrieve the digitalcontent 140. In some instances, selection of the link may require apurchase to retrieve the digital content. In other instances, selectionof the link may enable retrieval of the digital content 140 with adelayed purchase (e.g., at play time). The digital content subscribeinformation 270 may include user interface elements (e.g., link) thatmay be selected to subscribe to a feed (e.g., RSS feed) thatcommunicates (e.g., publishes) search result information 145 digitalcontent 140. In some instances, selection of the link may require apurchase to receive publications of the digital content. In otherinstances, selection of the link may enable receipt of publications ofthe digital content with a delayed purchase (e.g., at play time). Therequested information 272 includes information identified by the userfor retrieval form a data source 18. For example, the requestedinformation 272 may include ticket availability information for concertsof an artist that performs. The digital content streaming linkinformation 274 may include user interface elements that may be selectedto initiate streaming of the digital content 140.

FIG. 12 is a block diagram illustrating a database 26, according to anembodiment, coupled to the client machine 22 (e.g., control node). Thedatabase 26 may store output information folders 250, as previouslydescribed.

FIG. 13 is a block diagram illustrating a database 34, according to anembodiment, coupled to a portable client machine 32 (e.g., a portablemusic player). The database 34 may store digital content 140, aspreviously described.

FIG. 14 is flowchart illustrating a method 300, according to anembodiment, to retrieve search result information 145 and digitalcontent 140. Illustrated on the left panel is a portable client machine32 and illustrated in the right panel is a server machine 36.Illustrated in the middle left panel is a client machine 22 andillustrated in the middle right panel is a server machine 12. The method300 commences at operation 302, at the client machine 22, with thecommunication module 58 receiving input information 102. Thecommunication module 58 receives the input information 102 andcommunicates the input information 102 to the server machine 12.

At operation 304, at the server machine 12, the configuration module 50receives the input information 102. For example, the input information102 may identify an artist, Shawn Mullins, and request retrieval ofmusic videos authored by Shawn Mullins for communication to the clientmachine 22 and to the portable client machine 32. For example, the inputinformation 102 may include a folder title 200 (e.g., Shawn Mulllins),target identification information 202 (e.g., music videos, ticketavailability), search frequency information 204 (e.g., once a day), datasource information 206 (e.g., iTunes Store, etc.), release information208 (e.g., new releases), alert information 210 (e.g., communicate anemail if found), purchase information 212 (e.g., authorization to paybut not to exceed a predetermined limit) and storage information 214(e.g., authorization to retrieve but not to exceed a predeterminedlimit).

At operation 306, the configuration module 50 generates metadatainformation 104 based on the received input information 102. Atoperation 308, the configuration module 50 utilizes the search retrievalmetadata 118 to communicate commands (e.g., queries) to the data sources18 to retrieve the search result information 145.

At operation 308, the processing module 52 may use the target metadata120 to process the search result information 145. For example, theprocessing module 52 may use the target metadata 120 to identify targetinformation entries 123 in the search result information 145 that may beselected to retrieve a music video by Shawn Mullins. At operation 310,the server machine 36 may receive commands including queries from theserver machine 12 that may be processed to identify the search resultinformation 145 and communicate the search result information 145 backto the server machine 12.

At operation 312, the processing module 52 utilizes the digital contentretrieval metadata 124 and the search result information 145 to identifythe target information 147. Next, the recommendation engine 54 uses theprofile information 130 and the search result information 145 toidentify target information 147. Finally, the processing module 52utilizes the target information 147 to communicate commands includingqueries to the data sources to retrieve the digital content 140 from theserver machine 36.

At operation 314, the server machine 36 may receive commands includingqueries from the server machine 12 that may be processed to identify thedigital content 140 and communicate the digital content 140 back to theserver machine 12.

At operation 316, at the server machine 12, the processing module 52 maycommunicate the digital content information 254 and the targetinformation 147 to the client machine 22. For example, the digitalcontent information 254 may include digital content 140 in the form of aShawn Mullins music video and remote command information 133 tocommunicate the digital content 140 to a portable music player. Further,for example, the target information 147 may include the digital contentlink information 268 used to retrieve the Shawn Mullins music video andticket availability information for Shawn Mullins concerts.

At operation 318, at the client machine 22, the communication module 58receives the digital content information 254 and the target information147 and stores the digital content information 254 and the targetinformation 147 in the output information folder 125 associated withShawn Mullins.

At operation 320, at the client machine 22, the distribution module 60uses the media module identifier 262 to launch the appropriate mediamodule 56 (e.g., iTunes) to communicate the associated digital content140 to the portable client machine 32.

At operation 324, at the portable client machine 32, the portable mediamodule 66 receives the digital content 140 and stores the digitalcontent on the database 34.

In another embodiment, the input information 102 may be received fromthe portable client machine 32 and communicated to the server machine 12via the client machine 22. For example, at operation 301, the user mayenter input information 102 at the portable client machine 32 which, inturn, communicates the input information 102 to the client machine 22.At operation 303, at the client machine 22, the communication module 58may receive the input information 102 and communicate the inputinformation 102 to the server machine 12 (e.g., digital content hub).

It will further be appreciated that the above described method 300 toretrieve search result information 145 and digital content 140 may beinitiated responsive to receipt of input information 102 or responsiveto the configuration module 50 determining a search has been scheduledbased on search frequency information 204 associated with an inputinformation folder is requiring initiation.

FIG. 15 is a flowchart illustrating a method 308, according to anembodiment, to retrieve search result information 145. Illustrated onthe left panel are operations performed by the server machine 12 (e.g.,digital content hub) and illustrated on the right panel are operationsperformed by the server machines 36 (e.g., data sources 18). Withrespect to the left panel, operations on the left are performed by theprocessing module 52 operations on the right are performed by the mediamodule 56. The method 308 commences at operation 350 with the processingmodule 52 launching media modules 56 based on data source information206 in the input information folder 108 associated with Shawn Mullins.At operation 352, the configuration module 50 communicates a query forsearch result information 145. For example, the configuration module 50may use the local command metadata 126 to generate the appropriatecommands including queries to be communicated to the media module 56.Accordingly, one embodiment may include a sequence of commands toprovide a user name and password to the media module 56 and navigatethrough a series of user interfaces displayed by the media module 56before communicating a query to the media module 56 for the desireddigital content 140. At operation 354, the media module 56 receives thecommands including a query and communicates the commands to theappropriate server machine 36. At operation 356, at the data source 18,the query is received and at operation 358 the data source 18communicates the search result information 145 to the server machine 12.

At operation 360, at the server machine 12 (e.g., digital content hub),the media module 56 receives the search result information 145 and atoperation 354, the configuration module 50 scrapes the search resultinformation 145 from the media module 56 user interface.

At operation 366, the processing module 52, at the server machine 12,subscribes to a feed for search result information 145. For example, theprocessing module 52 may subscribe to a feed that advertises ShawnMullins music videos that are available for purchase on release of themusic video. At operation 368, at the server machine 12 (e.g., digitalcontent hub), the media module 56 receives and communicates thesubscription to the data source 18. At operation 370, the data source 18(e.g., iTunes Store) receives the subscription and at operation 372, thedata source 18 communicates the search result information 145 (e.g.,advertisement to purchase Shawn Mullins music video) to the servermachine 12 (e.g., digital content hub) responsive to the subscription.Further, at operation 372, the data source 18 continues to communicateor publish search result information 145 to the media module 56, at theserver machine 12 (e.g., digital content hub), as it becomes available.

At operation 374, at the server machine 12, the media module 56 (e.g.,iTunes) receives the search result information 145 and at operation 378,the configuration module 50 scrapes the search result information 145from the media module 56 user interface.

At operation 380, the processing module 52, at the server machine 12(e.g., digital content hub), processes the search result information 145to identify the target information 147. For example, the processingmodule 52 may use the parse metadata 128 that was generated based on thesearch information associated with a particular input information folder106 (e.g., Shawn Mullins) and the search result information 145 toidentify search result information entries 121 as target informationentries 123. The target information entries 123 may be in the form ofdigital content link information 268 or digital content subscribeinformation 270 or requested information 272 or digital contentstreaming link information 274.

At operation 382, the recommendation engine 54 parses the search resultinformation 145 to identify additional target information 147. Forexample, the recommendation engine 54 may use the profile information130 to parse the search result information entries 121 and associate arecommendation with each of the search result information entries 121.The recommendation engine 54 may use a star scheme with the highestrecommendation being four stars. In addition, the recommendation enginemay determine that a search result information entry 121 that isassociated with a recommendation that exceeds a predetermined thresholdis identified a target information entry 123. For example, a searchresult information entry 121 that is associated with a recommendation ofthree stars may exceed a predetermined threshold of two stars therebytriggering identification as a target information entry 123.

It will be appreciated that the above described method 308 to retrievesearch result information 145 may include launching multiple mediamodules 56 to retrieve the search result information 145. It willfurther be appreciated that the configuration module 50 is not requiredto utilize a media module 56 to retrieve the search result information145 but may communicate directly with the data sources via anapplication processing interface.

FIG. 16 is a flowchart illustrating a method 312, according to anembodiment, to retrieve digital content 140. Illustrated on the leftpanel are operations performed by the server machine 12 (e.g., digitalcontent hub), and illustrated on the right panel are operationsperformed by the data source 18. At the left panel and illustrated onthe left are operations performed by the processing module 52 andillustrated on the right are operations performed by the media module56. The method 400 commences at operation 402 at the server machine 12(e.g., digital content hub) with the processing module 52 identifyingdigital content 140 to retrieve. For example, the processing module 52may use the purchase metadata 134 and the storage metadata 136 todetermine whether to retrieve digital content 140 identified by digitalcontent link information 268. At operation 404, the processing module 52launches the appropriate media modules 56 to retrieve the digitalcontent 140. At operation 406, at the server machine 12 (e.g., digitalcontent hub), the processing module 52 communicates commands including aquery for a digital content 140 via the media module 56. At operation408, the media module 56 receives and communicates the query to theappropriate data source 18.

At operation 410, at the data source 18, the query is received and atoperation 412, the data source 18 communicates the digital content 140to the server machine 12 (e.g., digital content hub).

At operation 414, at the server machine 12 (e.g., digital content hub),the media module 56 receives the digital content 140. At operation 416,the processing module 52 stores the received digital content 140 in theappropriate output information folder 250. For example, a Shawn Mullinsmusic video would be stored in the Shawn Mullins folder. At operation417, the processing module 52 generates remote command information 133responsive to receipt of the digital content 140. For example, theprocessing module 52 may generate the digital content identifier 260 forthe Shawn Mullins music video, the media module identifier 262 toidentify the iTunes media module 56 and remote commands 264 to commandthe iTunes media module 56.

At operation 418, the processing module 52, subscribes to a feed fordigital content 140. For example, subscription to the feed may result inreceiving the digital content 140 as it is released. At operation 420,the media module 56 communicates the subscription to the appropriatedata source 18.

At operation 422, at the data source 18, the subscription is receivedand at operation 424, the data source 18 communicates or publishes thedigital content 140 to the server machine 12 (e.g., digital content hub)as it becomes available. At operation 426, at the server machine 12(e.g., digital content hub), the media module 56 receives the digitalcontent 140. At operation 428, the processing module 52 stores thepublished digital content 140 in the appropriate output informationfolder 250. At operation 430, the processing module 52 may generateremote command information 258 for the received digital content 140 andstore the remote command information 258 in the appropriate outputinformation folder 250.

It will be appreciated that multiple media modules 56 may be launched toretrieve the digital content 140. It will further be appreciated thatthe configuration module 50 need not utilize a media module 56 toretrieve the digital content 140 but may communicate directly with thedata sources 18 via an application processing interface.

Further, while the above described embodiment of the method 312describes a subscription for the digital content 140 that may becommunicated to the data source (e.g., iTunes Store) via the mediamodule 56 (e.g., iTunes) it will be appreciated that the subscriptionmay include a criterion to retrieve the digital content 140. Forexample, the criterion to retrieve the digital content may includesearch information 158 (e.g., release information 208) and/or filterinformation 160 (e.g., purchase information 212 and/or storageinformation 214), and/or an authorization to push the digital content140 based on a recommendation of the data source 18 (e.g., iTunesStore).

FIG. 17 is a flowchart illustrating a method 402, according to anembodiment, to identify digital content to retrieve. At decisionoperation 450, at the server machine 12 (e.g., digital content hub) theprocessing module 52 determines whether the next target informationentry 123 is a digital content link information 268. If the targetinformation entry 123 is digital content link information 268, then abranch is made to decision operation 454. Otherwise, processingcontinues at decision operation 452.

At decision operation 452, the processing module 52 determines if thetarget information entry 123 is a link to subscribe to digital content140 (e.g., digital content subscribe information 270). If the targetinformation entry 123 is digital content subscribe information 270, thena branch is made to decision operation 454. Otherwise, processingcontinues at decision operation 464.

At decision operation 454, the processing module 52 determines if apurchase is required to request the digital content 140 or to subscribefor the digital content 140. If a purchase is required, then a branch ismade to decision operation 456. Otherwise, if no purchase is required orpurchase may be delayed until after the request or subscription,processing continues at decision operation 458.

At decision operation 456, the processing module 52 determines if apurchase limitation is exceeded based on a predetermined pricelimitation. If the purchase limitation is exceeded, then a branch ismade to operation 460. Otherwise, processing continues at decisionoperation 458.

At decision operation 458, the processing module 52 determines if apredetermined storage limitation is exceeded based on a storagerequirement of the digital content 140. If the storage limitation isexceeded, then a branch is made to decision operation 464. Otherwise, abranch is made to operation 460.

At operation 460, the processing module 52 registers the digital content140 for retrieval. At operation 462, the processing module 52communicates an alert that includes notification information to apredetermined network address based on alert information 210. Forexample, the processing module 52 may communicate an email to an emailaddress that includes that notifies the recipient of receipt of thedigital content 140.

At decision operation 464, the processing module 52 determines if thereare more target information entries 123. If there are more targetinformation entries 123, a branch is made to operation 466 where theprocessing module 52 advances to the next target information entry 123.Otherwise, processing ends.

FIG. 18 is a flowchart illustrating a method 320, according to anembodiment, to communicate digital content 140 a portable client machine32 (e.g., iPod). The method 320 commences at the client machine 22(e.g., control node) with the distribution module 60 using the mediamodule identifier 262 to launch the appropriate media module 56. Forexample, the method 500 may commence responsive to receiving the digitalcontent 140 from the server machine 12 (e.g., digital content hub) orresponsive to a periodic scheduling. At operation 504, the distributionmodule 60 may utilize the remote commands 264 and the digital contentidentifier 260 to command the media module 56 to communicate the digitalcontent 140 that is identified to the portable client machine 32 (e.g.,iPod). At operation 506, the media module 56 communicates the digitalcontent 140 to the portable client machine 32 (e.g., iPod) and themethod ends.

FIG. 19 is a flowchart illustrating a method 506, according to anembodiment, to receive input information 102 from a portable clientmachine 32 (e.g., iPod) and communicate the input information 102 to theserver machine 12 (e.g., digital content hub). At operation 508, themethod 506 commences with the communication module 58 launching theappropriate media module 56. For example, the communication module 58may launch the media module 56 responsive to detecting a connection ofthe portable client machine 32 to the client machine 22. Otherembodiments may require the user to request input information 102 fromthe portable client machine 32. At operation 510, the communicationmodule 58 scrapes the input information 102 from the display generatedby the media module 56. At operation 512, the communication module 58communicates the input information 102 to the server machine 12 (e.g.,hub node) and the method ends.

FIG. 20 is a diagram illustrating a user interface 550, according to anembodiment, to receive input information 102. The user interface 550includes an interface control in the form of an input box 551 to receivea folder title 200 and other interface controls to receive targetidentification information 202. The folder title 200 may be used toidentify a pair of information folders including the input informationfolder 108 and the output information folder 106.

The interface controls to receive the target identification information202 include a pull down menu 552, an input box 554, and input checkboxes562-598. The pull down menu 552 may be used to receive a selection of anartist, creation, or category. The input box 554 may be used to receivethe name of an artist, the name of a creation, or the name of acategory.

The input checkboxes 562-598 may be used to receive requests fordifferent types (e.g., media types) of digital content 140 (e.g., musicvideos, digital sample, albums, streaming, image) and information (e.g.,ticket availability). The input checkboxes 562-568 may be used toreceive requests for a music video. The input checkbox 562 may be usedto receive a request to retrieve information about music videos for thenamed artist. Similarly, the input checkbox 564 may be used to receive arequest to retrieve digital content 140 and the input checkbox 566 maybe used to receive an authorization to purchase (e.g., if necessary forretrieval). Finally, the input checkbox 568 may be used to receive arequest to communicate an alert responsive retrieval of a music video.

The input checkboxes 570-574 may be used to receive the same requestsfor a digital sample. The input checkboxes 576-582 may be used toreceive the same requests for an album. The input checkboxes 584 may beused to receive the request for information for digital content 140 thatis streamed (e.g., links to initiate streaming). Finally, the inputcheckbox 596 may be used to receive a request for information aboutticket availability.

It will be appreciated that the user interface 500 is merely an exampleand that target identification information 202 may be received for othertypes of digital content 140 (e.g., multimedia presentations, slideshows, television episodes, movies, flash video files, etc.).

FIG. 21 is a diagram illustrating a user interface 600, according to anembodiment, to receive data source information 206, search frequencyinformation 204 and release information 208. The user interface 600 maybe presented to the user responsive to receiving a request to retrievesearch result information 145 (e.g., input checkboxes 562, 570, 576,584, 588, 596) via the user interface 550. The data source information206 may be received through input checkboxes 604-6145 that respectivelyidentify requests to retrieve search result information 145 and digitalcontent 140 from the identified data sources 18. Associated with thecheckbox 612 is a checkbox 613 to request communication of the digitalcontent 140 to the portable client machine(s) 32 (e.g., iPod). Thesearch frequency information 204 may be received via input checkbox616-620. The search frequency information 204 may be used to schedulesearches at a predetermined period. The release information 208 may bereceived from the input checkbox 624 and 626. The input checkbox 624 maybe used to receive a request to retrieve all releases of the digitalcontent. The input checkbox 626 may be used to receive a request toretrieve the latest released digital content.

FIG. 22 is a diagram illustrating a user interface 650, according to anembodiment, to receive storage information 214. The user interface 650may be presented to the user responsive to receiving a request toretrieve digital content 140 of a specified type (e.g., input checkboxes564, 572, 578, 590) via the user interface 550. The input box 654 may beused to receive a storage maximum limitation. The input box 656 may beused to receive a storage maximum per day limitation. The input box 658may be used to receive a storage rule limitation. The respective storagelimitations may be used by the server machine 12 (e.g., digital contenthub) to block retrieval of digital content 140 based on the storagerequirements of the digital content 140.

FIG. 23 is a diagram illustrating a user interface 670, according to anembodiment, to receive purchase information 212. The user interface 670may be presented to the user responsive to receiving a request topurchase digital content 140 of a specified type (e.g., input checkboxes566, 580, 592) via the user interface 550. The input box 674 may be usedto receive a one time purchase not to exceed limitation. The input box674 may be used to receive a one time purchase not to exceed limitation.The input box 676 may be used to receive a one month subscription not toexceed limitation. The input box 678 may be used to receive a yearsubscription not to exceed limitation. The input box 680 may be used toreceive a total purchases purchase not to exceed limitation. The inputbox 682 may be used to receive a purchase rule limitation. Therespective purchase limitations may be used by the server machine 12(e.g., digital content hub) to block retrieval of digital content 140based on the purchase requirements of the digital content 140.

FIG. 24 is the diagram illustrating a user interface 700, according toan embodiment, to receive alert information 210. The user interface 700may be presented to the user responsive to receiving a request tocommunicate an alert (e.g., input checkboxes 568, 574, 582, 594, 598)via the user interface 550. The alert information 210 may be receivedwith pull down menus 712, 716, and 720 respectively receiving anoperation status (e.g., enabled/disabled) for the respectivecommunication channels (e.g., email, instant messaging, cell phone). Itwill be appreciated that the alert information 210 may be received forany communication channel capable of communicating a message (e.g.,voice mail, VOIP, etc.). The alert information 210 may further bereceived from input boxes 714, 718, and 722 respectively receivingnetwork addresses for the respective communication channels.

FIG. 25 is a diagram illustrating a user interface 750, according to anembodiment, to receive recommendation information 162, global purchaseinformation 164 and global storage information 166. The recommendationinformation 162 may be received from input checkbox 752 and input boxes754, 756. The input checkbox 752 may receive an operation status (e.g.,enabled/disabled). Receiving an enabled operation status triggers therecommendation engine 54 to parse the search result information 145 andmake recommendations, as previously described. The input boxes 754, 756may receive a predetermined criterion that is used to determine whetherdigital content 140 is retrieved based on a recommendation. For example,the input box 754 is illustrated as receiving a predetermined criterionof three. Accordingly, in one embodiment, a search result informationentry 121 associated with a recommendation of three stars or greatertriggers retrieval of the corresponding digital content 140. Similarly,the input box 756 receives a predetermined criterion to determinewhether a recommendation to retrieve digital that requires a purchasemay be retrieved based on the recommendation. Accordingly, in oneembodiment, a search result information entry 121 associated with arecommendation of four stars or greater triggers payment and retrievalof the corresponding digital content 140.

The global purchase information 164 may be received via input boxes758-764 that respectively receive predetermined criteria or purchasinglimitations, as previously described but, in the present instance, asapplied to all purchases and not to purchases of a type of digitalcontent 140. The global purchase information 164 further includes inputboxes 766-772 for receiving payment method information that may be usedto purchase the digital content 140 via a payment system (e.g., PayPal,etc).

FIG. 26 is a diagram illustrating a user interface 800, according to anembodiment, to display folder information. The folder information mayinclude information contained in the input information folder 108,output information folder 106, and receipt information 810. Illustratedfrom right to left are tabs 802-808. The tab 802 may be selected to viewthe information contained in the input information folder 108 andinformation contained in the output information folder 106 associatedwith an artist (e.g., “Shawn Mullins”). Similarly, the tab 804 may beselected to view the folder information for a creation (e.g., televisionseries “24”) and the tab 806 may be selected to view the folderinformation for the category (e.g., “Best Pictures of the Year”).Finally, the tab 808 may be selected to view folder informationincluding receipt information 810 for purchase of the digital content140.

FIG. 27 is a diagram illustrating a user interface 850, according to anembodiment, to present information contained in an output informationfolder 106. The output information folder 106 includes text blocks 852,856, 858, 860, 862, 864, and 868 for describing target information 147for the artist, Shawn Mulllins and digital content 140 that has beenretrieved from the data sources 18 for the same artist. The text blocksmay include a recommendation (e.g. ****). The text blocks 852, 856, 858,860 describe digital content link information 268, according to anembodiment. The text block 862 describes digital content streaming linkinformation 274, according to an embodiment. The text block 862 includesa user interface element 866 that may be selected to initiate streaming.The text block 868 includes information that has been identified viarequested information 272 (e.g., ticket availability information),according to an embodiment. A user interface element 869 may be selectedfor further information about ticket availability.

The user interface 850 further includes text blocks 870, 872, and 874describing digital content 140 that was retrieved, according to anembodiment.

FIG. 28 is a diagram illustrating a user interface 900, according to anembodiment, to present receipt information 810. The receipt information810 includes a folder title column 902, associated with a set ofpayments for digital content 140, and method of payment information 906.Appearing under the folder title column 902 are the folder titles 200,as previously described. Illustrated are three payments for digitalcontent 140 to respective data sources 18 (e.g., awarstore.com,iTunes.com) aggregated into single transaction 904. For example, theserver machine 12 (digital content hub) may communicate with the paymentsystem 20 (e.g., PayPal) and the server machines 36 (e.g., data sources18) to conclude a single charge on the users financial instrument (e.g.,VISA, ATM, EFT, etc.) that balances a first payment to a server machine36 (e.g., awarestore.com) and a second payment to a different servermachine 36 (e.g., iTunes.com). Accordingly, the digital content hubprovides the advantage of simplifying payment for digital content 140 byautomatically aggregating multiple payments to financially independentdata sources 18 and a single charge to a financial instrument into asingle transaction.

It will be appreciated that other embodiments may receive the abovedescribed input information 102 utilizing an interface other than a userinterface. For example, the input information 102 may be received via anaudio interface, a machine interface, a kinetic interface (e.g., Wii), agraphical user interface or any other type of interface that may receivethe input information 102.

FIG. 29 shows a diagrammatic representation of machine in the exampleform of a computer system 1000 within which a set of instructions, forcausing the machine to perform any one or more of the methodologiesdiscussed herein, may be executed. In alternative embodiments, themachine operates as a standalone device or may be connected (e.g.,networked) to other machines. In a networked deployment, the machine mayoperate in the capacity of a server or a client machine in server-clientnetwork environment, or as a peer machine in a peer-to-peer (ordistributed) network environment. The machine may be a server computer,a client computer, a personal computer (PC), a tablet PC, a set-top box(STB), a Personal Digital Assistant (PDA), a cellular telephone, a webappliance, a network router, switch or bridge, or any machine capable ofexecuting a set of instructions (sequential or otherwise) that specifyactions to be taken by that machine. Further, while only a singlemachine is illustrated, the term “machine” shall also be taken toinclude any collection of machines that individually or jointly executea set (or multiple sets) of instructions to perform any one or more ofthe methodologies discussed herein.

The example computer system 1000 includes a processor 1002 (e.g., acentral processing unit (CPU) a graphics processing unit (GPU) or both),a main memory 1004 and a static memory 1006, which communicate with eachother via a bus 1008. The computer system 1000 may further include avideo display unit 1010 (e.g., a liquid crystal display (LCD) or acathode ray tube (CRT)). The computer system 1000 also includes analphanumeric input device 1012 (e.g., a keyboard), a cursor controldevice 1014 (e.g., a mouse), a disk drive unit 1016, a signal generationdevice 1018 (e.g., a speaker) and a network interface device 1020.

The disk drive unit 1016 includes a machine-readable medium 1022 onwhich is stored one or more sets of instructions (e.g., software 1024)embodying any one or more of the methodologies or functions describedherein. The software 1024 may also reside, completely or at leastpartially, within the main memory 1004 and/or within the processor 1002during execution thereof by the computer system 1000, the main memory1004 and the processor 1002 also constituting machine-readable media.

The software 1024 may further be transmitted or received over a network1026 via the network interface device 1020.

While the machine-readable medium 1022 is shown in an example embodimentto be a single medium, the term “machine-readable medium” should betaken to include a single medium or multiple media (e.g., a centralizedor distributed database, and/or associated caches and servers) thatstore the one or more sets of instructions. The term “machine-readablemedium” shall also be taken to include any medium that is capable ofstoring, encoding or carrying a set of instructions for execution by themachine and that cause the machine to perform any one or more of themethodologies of the present disclosure. The term “machine-readablemedium” shall accordingly be taken to include, but not be limited to,solid-state memories, optical and magnetic media, and carrier wavesignals.

Modules, Components and Logic

Certain embodiments are described herein as including logic or a numberof modules, components or mechanisms. A module, logic, component ormechanism (herein after collectively referred to as a “module”) may be atangible unit capable of performing certain operations and is configuredor arranged in a certain manner. In example embodiments, one or morecomputer systems (e.g., a standalone, client or server computer system)or one or more components of a computer system (e.g., a processor or agroup of processors) may be configured by software (e.g., an applicationor application portion) as a “module” that operates to perform certainoperations as described herein.

In various embodiments, a “module” may be implemented mechanically orelectronically. For example, a module may comprise dedicated circuitryor logic that is permanently configured (e.g., within a special-purposeprocessor) to perform certain operations. A module may also compriseprogrammable logic or circuitry (e.g., as encompassed within ageneral-purpose processor or other programmable processor) that istemporarily configured by software to perform certain operations. Itwill be appreciated that the decision to implement a modulemechanically, in the dedicated and permanently configured circuitry, orin temporarily configured circuitry (e.g., configured by software) maybe driven by cost and time considerations.

Accordingly, the term “module” should be understood to encompass atangible entity, be that an entity that is physically constructed,permanently configured (e.g., hardwired) or temporarily configured(e.g., programmed) to operate in a certain manner and/or to performcertain operations described herein. Considering embodiments in whichmodules or components are temporarily configured (e.g., programmed),each of the modules or components need not be configured or instantiatedat any one instance in time. For example, where the modules orcomponents comprise a general-purpose processor configured usingsoftware, the general-purpose processor may be configured as respectivedifferent modules at different times. Software may accordingly configurethe processor to constitute a particular module at one instance of timeand to constitute a different module at a different instance of time.

Modules can provide information to, and receive information from, othermodules. Accordingly, the described modules may be regarded as beingcommunicatively coupled. Where multiple of such modules existcontemporaneously, communications may be achieved through signaltransmission (e.g., over appropriate circuits and buses) that connectthe modules. In embodiments in which multiple modules are configured orinstantiated at different times, communications between such modules maybe achieved, for example, through the storage and retrieval ofinformation in memory structures to which the multiple modules haveaccess. For example, a one module may perform an operation, and storethe output of that operation in a memory device to which it iscommunicatively coupled. A further module may then, at a later time,access the memory device to retrieve and process the stored output.Modules may also initiate communications with input or output devices,and can operate on a resource (e.g., a collection of information).

Thus, methods and systems to retrieve search result information anddigital content have been described. Although the present disclosure hasbeen described with reference to specific example embodiments, it willbe evident that various modifications and changes may be made to theseembodiments without departing from the broader spirit and scope of thedisclosure. Accordingly, the specification and drawings are to beregarded in an illustrative rather than a restrictive sense.

The Abstract of the Disclosure is provided to comply with 37 C.F.R. §1.72(b), requiring an abstract that will allow the reader to quicklyascertain the nature of the technical disclosure. It is submitted withthe understanding that it will not be used to interpret or limit thescope or meaning of the claims. In addition, in the foregoing DetailedDescription, it can be seen that various features are grouped togetherin a single embodiment for the purpose of streamlining the disclosure.This method of disclosure is not to be interpreted as reflecting anintention that the claimed embodiments require more features than areexpressly recited in each claim. Rather, as the following claimsreflect, inventive subject matter lies in less than all features of asingle disclosed embodiment. Thus the following claims are herebyincorporated into the Detailed Description, with each claim standing onits own as a separate embodiment.

What is claimed is:
 1. A method comprising: collecting, at a servermachine, profile information of a user, the profile information compiledfrom observed user input information history over a period of time;periodically searching, at the server machine, based on user inputinformation, to create search results; identifying, at the servermachine, ticket information from the search results using the profileinformation, the ticket information pertaining to an event ticket;providing, by the server machine, the ticket information to the user;and automatically triggering payment and retrieval, by the servermachine, of the event ticket in accordance with a subscription of theuser.
 2. The method of claim 1, wherein providing the ticket informationto the user includes providing an alert to the user in response to aticket being available.
 3. The method of claim 1, wherein the ticketinformation includes information about an event corresponding to theevent ticket.
 4. The method of claim 3, wherein the information aboutthe event includes an artist performing at the event.
 5. The method ofclaim 1, wherein providing the ticket information to the user includessending a message to a mobile device of the user.
 6. A machine-readablemedium that is not a transitory propagating signal, the machine-readablemedium including instructions that, when executed by a machine; causethe machine to perform operations comprising: collecting, at a servermachine, profile information of a user, the profile information compiledfrom observed user input information history over a period of time;periodically searching, at the server machine, based on user inputinformation, to create search results; identifying, at the servermachine, ticket information from the search results using the profileinformation, the ticket information pertaining to an event ticket;providing, by the server machine, the ticket information to the user;and automatically triggering payment and retrieval, by the servermachine, of the event ticket in accordance with a subscription of theuser.
 7. The machine-readable medium of claim 6, wherein providing theticket information to the user includes providing an alert to the userin response to a ticket being available.
 8. The machine-readable mediumof claim 6, wherein the ticket information includes information about anevent corresponding to the event ticket.
 9. The machine-readable mediumof claim 8, wherein the information about the event includes an artistperforming at the event.
 10. The machine-readable medium of claim 6,wherein providing the ticket information to the user includes sending amessage to a mobile device of the user.
 11. A system comprising: a datasource including ticket information; and a server machinecommunicatively coupled to the data source, the server machine to:collect profile information of a user from Observed user inputinformation history over a period of time; periodically search the datasource based on user input information, to create search results;identify ticket information from the data source search results usingthe profile information, the ticket information pertaining to an eventticket; provide the ticket information to the user; and automaticallytrigger payment and retrieval, by the server machine, of the eventticket in accordance with a subscription of the user.
 12. The method ofclaim 11, wherein to provide the ticket information to the user includesthe server machine to provide an alert to the user in response to aticket being available.
 13. The method of claim 11, wherein the ticketinformation includes information about an event corresponding to theevent ticket.
 14. The method of claim 11, wherein to provide the ticketinformation to the user includes the server machine to send a message toa mobile device of the user.